Otto Kekäläinen [Mon, 22 Dec 2025 23:05:30 +0000 (15:05 -0800)]
Fix MariaDB build failure on amd64v3
Test patch from https://jira.mariadb.org/browse/MDEV-38398?focusedCommentId=319851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-319851
Confirmed to work on Launchpad builds. This will most likely be fixed in next
upstream release MariaDB 11.8.6 by upstream in a more elegant way, and this
patch should be kept in Debian (and Ubuntu) only temporairly.
Otto Kekäläinen [Thu, 27 Nov 2025 00:49:24 +0000 (16:49 -0800)]
Make the new merge_alter test indifferent to extra version info
Modify the test regex to accept any extra version info, just like it
accepts any server version info. The test is supposed to fail on actual
differences in behaviour and server info strings are intentionally
normalized and not regarded.
Without this modification, the test introduced in 9e8e215e would fail
in post-build MTR on "from Debian-log" and in autopkgtest on "from Debian":
main.merge_alter w4 [ fail ]
Test ended at 2025-11-26 22:41:38
CURRENT_TEST: main.merge_alter
/usr/share/mariadb/mariadb-test/main/merge_alter.result 2025-11-13 11:45:29.000000000 +0300
/tmp/tmp.3vGjZWHA79/var/4/log/merge_alter.reject 2025-11-27 01:41:38.523996124 +0300
@@ -10,7 +10,7 @@
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at #
-#010909 4:46:40 server id # end_log_pos # CRC32 XXX Start: binlog v 4, server v #.##.## created 010909 4:46:40 at startup
+#010909 4:46:40 server id # end_log_pos # CRC32 XXX Start: binlog v 4, server v #.##.## from Debian created 010909 4:46:40 at startup
ROLLBACK/*!*/;
# at #
#010909 4:46:40 server id # end_log_pos # CRC32 XXX Gtid list []
Result length mismatch
Forwarded: not-needed
Gbp-Pq: Name include-debian-in-test-merge-alter-result.patch
Otto Kekäläinen [Fri, 12 Dec 2025 08:53:33 +0000 (08:53 +0000)]
MDEV-37098 Fix Spider test failures in network-less environments
When running tests in environments without a network interface (such as
containers with `--network=none`), Spider could not retrieve a hardware
address to generate a node ID. This triggered a warning in the server
log, causing MTR to fail the test due to unexpected output:
[Warning] mariadbd: Can't get hardware address with error 2
Fix this by logging Spider hardware address errors to server log only.
This ensures the message is recorded in the server log for debugging but
does not pollute the client output.
It is questionable if this is a problem at all anyway, as when
`my_gethwaddr` fails, the code zeroes out the address buffer, resulting
in a `spider_unique_id` formatted like `-000000000000-PID-`, which is
valid.
When the test is starting up the server with innodb_force_recovery=1,
there will be messages about the LSN being in the future. The current
LSN is expected to be 12338 plus any number of FILE_CHECKPOINT records
(16 bytes each). We have observed anything up to 12402=12338+16*4 in
our CI systems. To be on the safe side, let us allow up to ten records.
Aquila Macedo [Sat, 8 Nov 2025 00:09:05 +0000 (21:09 -0300)]
[PATCH] MDEV-38046 Make func_regexp_pcre tolerant to PCRE2 offset change
PCRE2 10.47 reports the invalid escape in 'A\q' at offset 3 instead of 2.
Update the expected result and add a --replace_regex in the test so the
suite passes with both older and newer PCRE2 versions.
Forwarded: https://jira.mariadb.org/browse/MDEV-38046
(accepted upstream, will be in MariaDB 11.8.6+)
Otto Kekäläinen [Fri, 8 Aug 2025 04:30:51 +0000 (21:30 -0700)]
Suppress native AIO warning introduced in 10.8.3
Upstream a87bb96 introduced a new warning, visible at least on all ppc64el and
s390x builds which makes the post-build mariadb-test-test fail:
[Warning] InnoDB: native AIO failed: falling back to
innodb_use_native_aio=OFF
The case of this is the ci environment only where there is insufficent
fs.aio-max-nr configured. A such we are adding a suppression to the
mtr only. The warning is valuable for users. Upstream MDEV-37411 has
added a io_setup as a warning, which will fail in the CI environment,
so we're pre-emptively suppressing this warning too.
Unlike upstream MariaDB, in Debian we removed libaio in for Linux on
MariaDB 10.6+ in 612630c6 and completely in 1d648d6f. This was re-added
by upstream added a system variable innodb_linux_aio to control, and
also provided automated fallback. As such we're readding it back too.
With liburing still seccomp filterer in container environments having
a libaio fallback is more valuable than the threads implementation of
last resort.
Edited & Updated: Daniel Black <daniel@mariabdb.org>
Upstream rejected this with the conclusion, is that it will start working in
Debian/Salsa/Ubuntu/Launchpad once the Linux kernel is new enough to handle the
I/O calls and fallbacks properly, or once the CI system increases the value of
/proc/sys/fs/aio-max-nr to 1 million or so, to allow multiple parallel MariaDB
servers (as started by mariadb-test-run) each have enough quota for native AIO
to work.
Gbp-Pq: Name MDEV-37411-suppress-new-warning-about-native-aio.patch
Otto Kekalainen [Sun, 30 Jun 2024 15:18:06 +0000 (15:18 +0000)]
Disable the 'mysql*' command deprecation warning
Many command-line tools expect the commands they run to return without
any output in stderr or having error codes. The fact that now in MariaDB
11.4 all 'mysql*' commands emit a deprecation warning causes a lot of
scripts to fail, such as the /etc/init.d/mariadb itself and many dependent
programs as witnessed via Debian autopkgtests. See examples below.
Otto Kekalainen [Sun, 10 Mar 2024 16:56:13 +0000 (16:56 +0000)]
Show banner in server and client startup to drive community engagement
Suggest to users that they can support MariaDB development by simply giving a
star on GitHub. This patch experiments with how well such a banner works, and
may later change the contents to drive some other kind of engagement.
Client output:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 11.8.1-MariaDB-5 from Debian -- Please help get to 10k stars at https://github.com/MariaDB/Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
Server output:
[Note] Please help get to 10k stars at https://github.com/MariaDB/Server
Server output if built in git directory:
[Note] Starting MariaDB 11.8.1-MariaDB-5 from Debian source revision 1a9c3debfd6b1b16af4e501d3530b866b85c38a8 server_uid eNAjF8/wvUNM09/mSmh+k3a5o5w= as process 1359
Logs will also show as server output:
mysqld: Version: '11.8.1-MariaDB-5 from Debian' socket: '/run/mysqld/mysqld.sock' port: 3306 -- Please help get to 10k stars at https://github.com/MariaDB/Server
Upstream will never accept this patch,
see https://github.com/MariaDB/server/pull/1718
Origin: https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch
Forwarded: https://github.com/MariaDB/server/pull/1718 (rejected, will never be merged)
Otto Kekäläinen [Tue, 13 Jan 2026 19:03:57 +0000 (19:03 +0000)]
mariadb (1:11.8.5-4) unstable; urgency=medium
[ Otto Kekäläinen ]
* Add tentative upstream patch to fix amd64v3 build issues (MDEV-38398)
* Drop redundant `Priority: optional`
* Update Debian copyright for 2026
* Bump Debian Policy version
[ Aquila Macedo ]
* Drop obsolete library-not-linked-against-libc overrides
* Ship upstream sysusers.d mariadb.conf in mariadb-server (Closes: #1028271)
* Add patch sysusers-lock-mysql-account.patch
* Create mysql via sysusers in postinst, drop preinst adduser handling
* Drop adduser pre-depends, depend on systemd-sysusers provider
* Clarify NIS/YP debconf note for sysusers mysql account creation
* Update all translations to match updated template
Otto Kekäläinen [Thu, 27 Nov 2025 00:49:24 +0000 (16:49 -0800)]
Make the new merge_alter test indifferent to extra version info
Modify the test regex to accept any extra version info, just like it
accepts any server version info. The test is supposed to fail on actual
differences in behaviour and server info strings are intentionally
normalized and not regarded.
Without this modification, the test introduced in 9e8e215e would fail
in post-build MTR on "from Debian-log" and in autopkgtest on "from Debian":
main.merge_alter w4 [ fail ]
Test ended at 2025-11-26 22:41:38
CURRENT_TEST: main.merge_alter
/usr/share/mariadb/mariadb-test/main/merge_alter.result 2025-11-13 11:45:29.000000000 +0300
/tmp/tmp.3vGjZWHA79/var/4/log/merge_alter.reject 2025-11-27 01:41:38.523996124 +0300
@@ -10,7 +10,7 @@
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at #
-#010909 4:46:40 server id # end_log_pos # CRC32 XXX Start: binlog v 4, server v #.##.## created 010909 4:46:40 at startup
+#010909 4:46:40 server id # end_log_pos # CRC32 XXX Start: binlog v 4, server v #.##.## from Debian created 010909 4:46:40 at startup
ROLLBACK/*!*/;
# at #
#010909 4:46:40 server id # end_log_pos # CRC32 XXX Gtid list []
Result length mismatch
Forwarded: not-needed
Gbp-Pq: Name include-debian-in-test-merge-alter-result.patch
Otto Kekäläinen [Fri, 12 Dec 2025 08:53:33 +0000 (08:53 +0000)]
MDEV-37098 Fix Spider test failures in network-less environments
When running tests in environments without a network interface (such as
containers with `--network=none`), Spider could not retrieve a hardware
address to generate a node ID. This triggered a warning in the server
log, causing MTR to fail the test due to unexpected output:
[Warning] mariadbd: Can't get hardware address with error 2
Fix this by logging Spider hardware address errors to server log only.
This ensures the message is recorded in the server log for debugging but
does not pollute the client output.
It is questionable if this is a problem at all anyway, as when
`my_gethwaddr` fails, the code zeroes out the address buffer, resulting
in a `spider_unique_id` formatted like `-000000000000-PID-`, which is
valid.
When the test is starting up the server with innodb_force_recovery=1,
there will be messages about the LSN being in the future. The current
LSN is expected to be 12338 plus any number of FILE_CHECKPOINT records
(16 bytes each). We have observed anything up to 12402=12338+16*4 in
our CI systems. To be on the safe side, let us allow up to ten records.
Aquila Macedo [Sat, 8 Nov 2025 00:09:05 +0000 (21:09 -0300)]
[PATCH] MDEV-38046 Make func_regexp_pcre tolerant to PCRE2 offset change
PCRE2 10.47 reports the invalid escape in 'A\q' at offset 3 instead of 2.
Update the expected result and add a --replace_regex in the test so the
suite passes with both older and newer PCRE2 versions.
Forwarded: https://jira.mariadb.org/browse/MDEV-38046
(accepted upstream, will be in MariaDB 11.8.6+)
Otto Kekäläinen [Fri, 8 Aug 2025 04:30:51 +0000 (21:30 -0700)]
Suppress native AIO warning introduced in 10.8.3
Upstream a87bb96 introduced a new warning, visible at least on all ppc64el and
s390x builds which makes the post-build mariadb-test-test fail:
[Warning] InnoDB: native AIO failed: falling back to
innodb_use_native_aio=OFF
The case of this is the ci environment only where there is insufficent
fs.aio-max-nr configured. A such we are adding a suppression to the
mtr only. The warning is valuable for users. Upstream MDEV-37411 has
added a io_setup as a warning, which will fail in the CI environment,
so we're pre-emptively suppressing this warning too.
Unlike upstream MariaDB, in Debian we removed libaio in for Linux on
MariaDB 10.6+ in 612630c6 and completely in 1d648d6f. This was re-added
by upstream added a system variable innodb_linux_aio to control, and
also provided automated fallback. As such we're readding it back too.
With liburing still seccomp filterer in container environments having
a libaio fallback is more valuable than the threads implementation of
last resort.
Edited & Updated: Daniel Black <daniel@mariabdb.org>
Upstream rejected this with the conclusion, is that it will start working in
Debian/Salsa/Ubuntu/Launchpad once the Linux kernel is new enough to handle the
I/O calls and fallbacks properly, or once the CI system increases the value of
/proc/sys/fs/aio-max-nr to 1 million or so, to allow multiple parallel MariaDB
servers (as started by mariadb-test-run) each have enough quota for native AIO
to work.
Gbp-Pq: Name MDEV-37411-suppress-new-warning-about-native-aio.patch
Otto Kekalainen [Sun, 30 Jun 2024 15:18:06 +0000 (15:18 +0000)]
Disable the 'mysql*' command deprecation warning
Many command-line tools expect the commands they run to return without
any output in stderr or having error codes. The fact that now in MariaDB
11.4 all 'mysql*' commands emit a deprecation warning causes a lot of
scripts to fail, such as the /etc/init.d/mariadb itself and many dependent
programs as witnessed via Debian autopkgtests. See examples below.
Otto Kekalainen [Sun, 10 Mar 2024 16:56:13 +0000 (16:56 +0000)]
Show banner in server and client startup to drive community engagement
Suggest to users that they can support MariaDB development by simply giving a
star on GitHub. This patch experiments with how well such a banner works, and
may later change the contents to drive some other kind of engagement.
Client output:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 11.8.1-MariaDB-5 from Debian -- Please help get to 10k stars at https://github.com/MariaDB/Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
Server output:
[Note] Please help get to 10k stars at https://github.com/MariaDB/Server
Server output if built in git directory:
[Note] Starting MariaDB 11.8.1-MariaDB-5 from Debian source revision 1a9c3debfd6b1b16af4e501d3530b866b85c38a8 server_uid eNAjF8/wvUNM09/mSmh+k3a5o5w= as process 1359
Logs will also show as server output:
mysqld: Version: '11.8.1-MariaDB-5 from Debian' socket: '/run/mysqld/mysqld.sock' port: 3306 -- Please help get to 10k stars at https://github.com/MariaDB/Server
Upstream will never accept this patch,
see https://github.com/MariaDB/server/pull/1718
Origin: https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch
Forwarded: https://github.com/MariaDB/server/pull/1718 (rejected, will never be merged)
Otto Kekäläinen [Tue, 16 Dec 2025 04:00:00 +0000 (20:00 -0800)]
mariadb (1:11.8.5-3) unstable; urgency=medium
* MDEV-23538: Rename mariadb.pc to mariadb-server-embedded.pc to avoid
confusion, as well as sync other misc Debian packaging improvements from
upstream
* Drop transitional dummy package `mariadb-server-10.5`
* Make mariadb-test-run logs more informative to make debugging failures
in Debian/Ubuntu build and autopkgtest logs easier
* Remove override for test 'main.mysql-interactive' and extensively document
and ensure all the mariadb-test-run skip lists are current
* Add tentative upstream patch to fix main.mysqld--help-aria test failure
* Add upstream patch to fix test innodb_log_file_size failures
* Add upstream patch to fix test innodb.log_corruption_recovery failures
* Add patch to fix Spider test failures in networkless environments
Otto Kekalainen [Sun, 30 Jun 2024 15:18:06 +0000 (15:18 +0000)]
Disable the 'mysql*' command deprecation warning
Many command-line tools expect the commands they run to return without
any output in stderr or having error codes. The fact that now in MariaDB
11.4 all 'mysql*' commands emit a deprecation warning causes a lot of
scripts to fail, such as the /etc/init.d/mariadb itself and many dependent
programs as witnessed via Debian autopkgtests. See examples below.
Otto Kekalainen [Sun, 10 Mar 2024 16:56:13 +0000 (16:56 +0000)]
Show banner in server and client startup to drive community engagement
Suggest to users that they can support MariaDB development by simply giving a
star on GitHub. This patch experiments with how well such a banner works, and
may later change the contents to drive some other kind of engagement.
Client output:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 11.8.1-MariaDB-5 from Debian -- Please help get to 10k stars at https://github.com/MariaDB/Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
Server output:
[Note] Please help get to 10k stars at https://github.com/MariaDB/Server
Server output if built in git directory:
[Note] Starting MariaDB 11.8.1-MariaDB-5 from Debian source revision 1a9c3debfd6b1b16af4e501d3530b866b85c38a8 server_uid eNAjF8/wvUNM09/mSmh+k3a5o5w= as process 1359
Logs will also show as server output:
mysqld: Version: '11.8.1-MariaDB-5 from Debian' socket: '/run/mysqld/mysqld.sock' port: 3306 -- Please help get to 10k stars at https://github.com/MariaDB/Server
Daniel Black [Mon, 29 Jan 2024 03:51:30 +0000 (19:51 -0800)]
mariadb: FTBFS on hurd-i386: undefined reference to misc functions and files requires https://github.com/MariaDB/server/pull/2893 as debian explicit architectures aren't needed since dh_auto_configure handles this.
If it works, upstream welcome.
Hurd string from uname -m, "SYSTEM processor: i686-AT386" in mariadb
output. And wiki reference https://en.wikipedia.org/wiki/Uname
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006531
Forwarded: no
Upstream will never accept this patch,
see https://github.com/MariaDB/server/pull/1718
Origin: https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch
Forwarded: https://github.com/MariaDB/server/pull/1718 (rejected, will never be merged)
Otto Kekäläinen [Sun, 8 Jun 2025 08:19:07 +0000 (11:19 +0300)]
mariadb (1:11.8.2-1) unstable; urgency=medium
* New upstream version 11.8.2, which also announces the 11.8 series now
ready for general availability (GA) with security releases for 5 years.
This release includes fixes for several defects as noted at
https://mariadb.com/kb/en/mariadb-11-8-2-release-notes/ as well
the following security issues (Closes: #1100437, #1105976):
- CVE-2023-52969
- CVE-2023-52970
- CVE-2023-52971
- CVE-2025-30693
- CVE-2025-30722
* Drop all RocksDB patches now upstream due to update to version 6.29fb
* Drop PCRE2 10.45 compatibility patch obsoleted by upstream test change
* Update configuration traces to include new upstream system variables:
- innodb-buffer-pool-size-auto-min (default: 0)
- innodb-buffer-pool-size-max (default: 0)
- innodb-log-checkpoint-now (default: FALSE)
* Also update configuration traces to match that in 11.8.2 the variables
innodb-buffer-pool-chunk-size and innodb-log-spin-wait-delay are advertised
as deprecated.
* Disable new unreliable test main.mysql-interactive
* Add Breaks/Replaces for files moved around in src:mysql-8.4 (LP: #2110378)
* Update mariadb-server.NEWS with information about MariaDB 11.8 and
* best practices for creating app user and allowing remote connections
* Add patch to improve output from mariadb-secure-installation
Sam Bull [Tue, 5 Nov 2024 12:44:58 +0000 (12:44 +0000)]
MDEV-36009: Systemd: Restart on OOM
Per https://github.com/systemd/systemd/issues/36529 OOM counts
as a on-abnormal condition. To ensure that MariaDB testart on
OOM the Restart is changes to on-abnormal which an extension
on the current on-abort condition.
Matthew Vernon [Thu, 6 Feb 2025 14:44:19 +0000 (14:44 +0000)]
Update PCRE tests to fix case confusion (Closes: #1095286)
MariaDB RLIKE is case-insensitive; in perl the Unicode character
property tests \p{Lu} and \p{Ll} are equivalent to \p{L&} in
case-insensitive matches. So remove those tests (since there is
already the \p{L&} test).
This fixes a FTBFS with PCRE2 10.45 which fixed its handling of Ll Lt
and Lu under case-insensitive matching to match perl's behaviour.
Example of failure seen in MTR:
main.func_regexp_pcre w4 [ fail ]
Test ended at 2025-02-06 07:00:25
CURRENT_TEST: main.func_regexp_pcre
@@ -169,13 +169,13 @@
\p{Latin} 㐗 0
\p{Latin} 갷 0
\p{Ll} 1 0
-\p{Ll} A 0
+\p{Ll} A 1
\p{Ll} a 1
-\p{Ll} À 0
+\p{Ll} À 1
\p{Ll} à 1
-\p{Ll} Σ 0
+\p{Ll} Σ 1
\p{Ll} σ 1
-\p{Ll} Я 0
+\p{Ll} Я 1
\p{Ll} я 1
\p{Ll} ௨ 0
\p{Ll} ප 0
Forwarded: no
Gbp-Pq: Name 1095286-pcre-tests-case-confusion.patch
Otto Kekalainen [Sun, 30 Jun 2024 15:18:06 +0000 (15:18 +0000)]
Disable the 'mysql*' command deprecation warning
Many command-line tools expect the commands they run to return without
any output in stderr or having error codes. The fact that now in MariaDB
11.4 all 'mysql*' commands emit a deprecation warning causes a lot of
scripts to fail, such as the /etc/init.d/mariadb itself and many dependent
programs as witnessed via Debian autopkgtests. See examples below.
Otto Kekalainen [Sun, 10 Mar 2024 16:56:13 +0000 (16:56 +0000)]
Show banner in server and client startup to drive community engagement
Suggest to users that they can support MariaDB development by simply giving a
star on GitHub. This patch experiments with how well such a banner works, and
may later change the contents to drive some other kind of engagement.
Client output:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 34
Server version: 10.11.7-MariaDB-3 Debian n/a
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Support MariaDB developers by giving a star at https://github.com/MariaDB/server
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
Server output:
[Note] Support MariaDB developers by giving a star at https://github.com/MariaDB/server
Daniel Black [Mon, 29 Jan 2024 03:51:30 +0000 (19:51 -0800)]
mariadb: FTBFS on hurd-i386: undefined reference to misc functions and files requires https://github.com/MariaDB/server/pull/2893 as debian explicit architectures aren't needed since dh_auto_configure handles this.
If it works, upstream welcome.
Hurd string from uname -m, "SYSTEM processor: i686-AT386" in mariadb
output. And wiki reference https://en.wikipedia.org/wiki/Uname
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006531
Forwarded: no
Otto Kekalainen [Wed, 30 Jun 2021 04:08:05 +0000 (21:08 -0700)]
Make RocksDB build reproducible
The RocksDB binary included a string with the build timestamp:
> rocksdb_build_git_date:@2021-05-23-16:04:38@
As this changes from build to build, it makes the builds unreproducible.
Simply removing it solves the issue.
This temporary fix can be removed when a proper fix already done in upstream
lands in MariaDB when the RocksDB submodule is updated to a newer release.
Origin: https://github.com/facebook/rocksdb/commit/0a9a05ae12943b1529ef1eabbca5ce5a71c986bf
Bug: https://github.com/facebook/rocksdb/issues/7035
# Merged in RocksDB 6.19.3, but not updated into MariaDB yet
Gbp-Pq: Name fix-reproducible-builds-rocksdb.patch
Otto Kekalainen [Thu, 3 Mar 2022 02:13:18 +0000 (18:13 -0800)]
Fix various spelling errors still found in code
Two upstream PRs remain that have been merged, but not imported on MariaDB yet.
Forwarded: https://github.com/facebook/rocksdb/pull/9653
Origin: https://patch-diff.githubusercontent.com/raw/facebook/rocksdb/pull/9653.patch
# Merged in RocksDB 7.3.1, but not updated into MariaDB yet
Upstream will never accept this patch,
see https://github.com/MariaDB/server/pull/1718
Origin: https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch
Forwarded: https://github.com/MariaDB/server/pull/1718 (rejected, will never be merged)
Andrew Kryczka [Wed, 17 Jun 2020 02:34:21 +0000 (19:34 -0700)]
rocksdb-kfreebsd
Upstream has merged this but we still need to wait for it to be included
in a RocksDB release and imported into MariaDB and then into Debian.
Bug: https://jira.mariadb.org/browse/MDEV-19251
Forwarded: https://github.com/facebook/rocksdb/pull/6992
# Merged in RocksDB 6.12.6 but not updated into MariaDB yet
Otto Kekäläinen [Wed, 23 Apr 2025 14:29:38 +0000 (07:29 -0700)]
mariadb (1:11.8.1-4) unstable; urgency=medium
* Disable main.mysqld--help-aria test that failed on nearly every
architecture in previous upload due to new upstream issue (MDEV-36334)
* Disable some vector related tests that failed on sparc64 (MDEV-36670)
* Backport main.func_format fix for exabyte/petabyte mismatch on i386
Matthew Vernon [Thu, 6 Feb 2025 14:44:19 +0000 (14:44 +0000)]
Update PCRE tests to fix case confusion (Closes: #1095286)
MariaDB RLIKE is case-insensitive; in perl the Unicode character
property tests \p{Lu} and \p{Ll} are equivalent to \p{L&} in
case-insensitive matches. So remove those tests (since there is
already the \p{L&} test).
This fixes a FTBFS with PCRE2 10.45 which fixed its handling of Ll Lt
and Lu under case-insensitive matching to match perl's behaviour.
Example of failure seen in MTR:
main.func_regexp_pcre w4 [ fail ]
Test ended at 2025-02-06 07:00:25
CURRENT_TEST: main.func_regexp_pcre
@@ -169,13 +169,13 @@
\p{Latin} 㐗 0
\p{Latin} 갷 0
\p{Ll} 1 0
-\p{Ll} A 0
+\p{Ll} A 1
\p{Ll} a 1
-\p{Ll} À 0
+\p{Ll} À 1
\p{Ll} à 1
-\p{Ll} Σ 0
+\p{Ll} Σ 1
\p{Ll} σ 1
-\p{Ll} Я 0
+\p{Ll} Я 1
\p{Ll} я 1
\p{Ll} ௨ 0
\p{Ll} ප 0
Forwarded: no
Gbp-Pq: Name 1095286-pcre-tests-case-confusion.patch
Otto Kekalainen [Sun, 30 Jun 2024 15:18:06 +0000 (15:18 +0000)]
Disable the 'mysql*' command deprecation warning
Many command-line tools expect the commands they run to return without
any output in stderr or having error codes. The fact that now in MariaDB
11.4 all 'mysql*' commands emit a deprecation warning causes a lot of
scripts to fail, such as the /etc/init.d/mariadb itself and many dependent
programs as witnessed via Debian autopkgtests. See examples below.
Otto Kekalainen [Sun, 10 Mar 2024 16:56:13 +0000 (16:56 +0000)]
Show banner in server and client startup to drive community engagement
Suggest to users that they can support MariaDB development by simply giving a
star on GitHub. This patch experiments with how well such a banner works, and
may later change the contents to drive some other kind of engagement.
Client output:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 34
Server version: 10.11.7-MariaDB-3 Debian n/a
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Support MariaDB developers by giving a star at https://github.com/MariaDB/server
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
Server output:
[Note] Support MariaDB developers by giving a star at https://github.com/MariaDB/server
Daniel Black [Mon, 29 Jan 2024 03:51:30 +0000 (19:51 -0800)]
mariadb: FTBFS on hurd-i386: undefined reference to misc functions and files requires https://github.com/MariaDB/server/pull/2893 as debian explicit architectures aren't needed since dh_auto_configure handles this.
If it works, upstream welcome.
Hurd string from uname -m, "SYSTEM processor: i686-AT386" in mariadb
output. And wiki reference https://en.wikipedia.org/wiki/Uname
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006531
Forwarded: no
Otto Kekalainen [Wed, 30 Jun 2021 04:08:05 +0000 (21:08 -0700)]
Make RocksDB build reproducible
The RocksDB binary included a string with the build timestamp:
> rocksdb_build_git_date:@2021-05-23-16:04:38@
As this changes from build to build, it makes the builds unreproducible.
Simply removing it solves the issue.
This temporary fix can be removed when a proper fix already done in upstream
lands in MariaDB when the RocksDB submodule is updated to a newer release.
Origin: https://github.com/facebook/rocksdb/commit/0a9a05ae12943b1529ef1eabbca5ce5a71c986bf
Bug: https://github.com/facebook/rocksdb/issues/7035
# Merged in RocksDB 6.19.3, but not updated into MariaDB yet
Gbp-Pq: Name fix-reproducible-builds-rocksdb.patch
Otto Kekalainen [Thu, 3 Mar 2022 02:13:18 +0000 (18:13 -0800)]
Fix various spelling errors still found in code
Two upstream PRs remain that have been merged, but not imported on MariaDB yet.
Forwarded: https://github.com/facebook/rocksdb/pull/9653
Origin: https://patch-diff.githubusercontent.com/raw/facebook/rocksdb/pull/9653.patch
# Merged in RocksDB 7.3.1, but not updated into MariaDB yet
Upstream will never accept this patch,
see https://github.com/MariaDB/server/pull/1718
Origin: https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch
Forwarded: https://github.com/MariaDB/server/pull/1718 (rejected, will never be merged)
Andrew Kryczka [Wed, 17 Jun 2020 02:34:21 +0000 (19:34 -0700)]
rocksdb-kfreebsd
Upstream has merged this but we still need to wait for it to be included
in a RocksDB release and imported into MariaDB and then into Debian.
Bug: https://jira.mariadb.org/browse/MDEV-19251
Forwarded: https://github.com/facebook/rocksdb/pull/6992
# Merged in RocksDB 6.12.6 but not updated into MariaDB yet
Otto Kekäläinen [Thu, 20 Mar 2025 19:31:04 +0000 (12:31 -0700)]
mariadb (1:11.8.1-2) unstable; urgency=medium
* Disable test func_format on i386 (MDEV-36334) to get i386 builds
pass on official Debian buildd while upstream fixes the issue
* Restore better error message on service stop failures from c789cdaf
* Revert "Set CAP_IPC_LOCK capability if possible" to follow upstream
Matthew Vernon [Thu, 6 Feb 2025 14:44:19 +0000 (14:44 +0000)]
Update PCRE tests to fix case confusion (Closes: #1095286)
MariaDB RLIKE is case-insensitive; in perl the Unicode character
property tests \p{Lu} and \p{Ll} are equivalent to \p{L&} in
case-insensitive matches. So remove those tests (since there is
already the \p{L&} test).
This fixes a FTBFS with PCRE2 10.45 which fixed its handling of Ll Lt
and Lu under case-insensitive matching to match perl's behaviour.
Example of failure seen in MTR:
main.func_regexp_pcre w4 [ fail ]
Test ended at 2025-02-06 07:00:25
CURRENT_TEST: main.func_regexp_pcre
@@ -169,13 +169,13 @@
\p{Latin} 㐗 0
\p{Latin} 갷 0
\p{Ll} 1 0
-\p{Ll} A 0
+\p{Ll} A 1
\p{Ll} a 1
-\p{Ll} À 0
+\p{Ll} À 1
\p{Ll} à 1
-\p{Ll} Σ 0
+\p{Ll} Σ 1
\p{Ll} σ 1
-\p{Ll} Я 0
+\p{Ll} Я 1
\p{Ll} я 1
\p{Ll} ௨ 0
\p{Ll} ප 0
Forwarded: no
Gbp-Pq: Name 1095286-pcre-tests-case-confusion.patch
Otto Kekalainen [Sun, 30 Jun 2024 15:18:06 +0000 (15:18 +0000)]
Disable the 'mysql*' command deprecation warning
Many command-line tools expect the commands they run to return without
any output in stderr or having error codes. The fact that now in MariaDB
11.4 all 'mysql*' commands emit a deprecation warning causes a lot of
scripts to fail, such as the /etc/init.d/mariadb itself and many dependent
programs as witnessed via Debian autopkgtests. See examples below.
projects / mariadb.git / log